Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: Improve row state evaluation on a complex lazily loaded screens #1877

Merged

Conversation

urbanekv
Copy link
Contributor

@urbanekv urbanekv commented Sep 7, 2023

Improved row state evaluation on a complex lazily loaded screens. Refactored RowSecurityState building process - separated into a new class RowSecurityStateBuilder. Optimization - build only what is needed for all callers.

…#1854)

Improved row state evaluation on a complex lazily loaded screens. 
Refactored RowSecurityState building process  - separated into a new class RowSecurityStateBuilder. 
Optimization - build only what is needed for all callers.

---------

Co-authored-by: Václav Urbánek <vaclav.urbanek@advantages.cz>
Co-authored-by: Petr Hrehorovsky <83349812+washibana@users.noreply.github.com>
@urbanekv urbanekv changed the title FIX: Improve row state evaluation on a complex lazily loaded screens #1854 FIX: Improve row state evaluation on a complex lazily loaded screens Sep 7, 2023
@origambot
Copy link

This pull request has been mentioned on ORIGAM Community. There might be relevant details there:

https://community.origam.com/t/rowstates-on-complex-lazily-loaded-screens-are-very-slow-when-compared-to-a-desktop-client/2991/5

@washibana washibana merged commit 482e861 into master Sep 7, 2023
10 checks passed
@washibana washibana deleted the improve-rowstates-on-complex-lazily-loaded-screens-master branch September 7, 2023 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants